-- Network Working Group H. Alvestrand
-- Request for Comments: 2157 UNINETT
-- Category: Standards Track January 1998-- Mapping between X.400 and RFC-822/MIME Message BodiesMIXER-MAPPINGS DEFINITIONS::=BEGINEXPORTS-- everything --;IMPORTSmixer -- { iso(1) org(3) dod(6) internet(1) mail(7) mixer(1) }
--PSIM(correct, but not supported by all compiler) FROM MIXER -¤-Companion RFC-¤-;FROM MIXER;mixer-headings OBJECTIDENTIFIER::={ mixer 1}-- called mime-mhs-headings in RFC 1495 --
mixer-bodies OBJECTIDENTIFIER::={ mixer 2}-- called mime-mhs-bodies in RFC 1495 ---- mixer-core is defined as { mixer core(3) } in [MIXER]mixer-bp-data OBJECTIDENTIFIER::=--PSIM { mixer-bodies 1 }; -¤- called mime-mhs-bp-data in RFC 1494 --{ mixer-bodies 1}-- called mime-mhs-bp-data in RFC 1494 --mixer-bp-parameter OBJECTIDENTIFIER::=--PSIM { mixer-bodies 2 };{ mixer-bodies 2}id-mime-bp-data OBJECTIDENTIFIER::=--PSIM { mixer-bp-data 1 };{ mixer-bp-data 1}-- for debugging: mixer-bp-data is 1.3.6.1.7.1.2.1.1id-mime-bp-parameters OBJECTIDENTIFIER::=
--PSIM { mixer-bp-parameter 1 };{ mixer-bp-parameter 1}-- the following assignments were done in RFC 1494, using-- slightly different names, but the same numbers.-- their defining text is now is now in other documentsid-mime-postscript-body OBJECTIDENTIFIER::={ mixer-bp-data 2}id-mime-jpeg-body OBJECTIDENTIFIER::={ mixer-bp-data 3}id-mime-gif-body OBJECTIDENTIFIER::={ mixer-bp-data 4}-- This is a new definition, and defines an FTAM application reference,-- not a BP15 data OID.id-mime-ftbp-data OBJECTIDENTIFIER::=
{ mixer-bp-data 5}-- The following heading extensions are definedid-hex-partial-message OBJECTIDENTIFIER::={ mixer-headings 1}id-hex-multipart-message OBJECTIDENTIFIER::={ mixer-headings 2}-- from RFC 1495; obsoleteid-hex-multipart-message-v2 OBJECTIDENTIFIER::={ mixer-headings 3}END